Better templates file handling (copying, renaming, replacing content) #497
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PG usually copy files from templates folder to project
renames them (or rename in the copy process)
replaces content inside of them (opening and saving)
this PR creates an object to hold the input file path (template), output file path (project) and replacement pairs
so it can do a straight copy if no replacements are asked
or open the files from source (template)
replaces content
and write definitive content in the project folder.
it also address a problem in msys2 where std::filesystem is not considering overwrite_existing and throwing errors. it removes destination file before copying in msys2 only.